Delay bug in expr adjustment when check_expr is called multiple times #94596
+50
−11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rustbot
added
the
T-compiler
|
r? @estebank (rust-highfive has picked a reviewer for you, use r? to override) |
rust-highfive
added
the
S-waiting-on-review
estebank
added
the
beta-nominated
|
@bors r+ |
|
📌 Commit 8af683d has been approved by |
bors
added
S-waiting-on-bors
|
Beta nominated as it addresses #94511. |
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Mar 5, 2022
Rollup of 5 pull requests Successful merges: - rust-lang#94362 (Add well known values to `--check-cfg` implementation) - rust-lang#94577 (only disable SIMD for doctests in Miri (not for the stdlib build itself)) - rust-lang#94595 (Fix invalid `unresolved imports` errors for a single-segment import) - rust-lang#94596 (Delay bug in expr adjustment when check_expr is called multiple times) - rust-lang#94618 (Don't round stack size up for created threads in Windows) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Closed
rustbot
added
the
beta-accepted
Mark-Simulacrum
removed
the
beta-nominated
Merged
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Mar 14, 2022
…ulacrum [beta] backports * Update LLVM submodule rust-lang#94764 * Statically compile libstdc++ everywhere if asked rust-lang#94719 * Downgrade #[test] on macro call to warning rust-lang#94624 * Delay bug in expr adjustment when check_expr is called multiple times rust-lang#94596 * bootstrap: correct reading of flags for llvm rust-lang#94466 * Check method input expressions once rust-lang#94438 * remove feature gate in control_flow examples rust-lang#94283 r? `@Mark-Simulacrum`
bors
added a commit
to rust-lang-ci/rust
that referenced
this pull request
Mar 22, 2022
…k-Simulacrum [beta] Remove statement that was forgotten when backporting rust-lang#94596 This `if` statement was introduced in rust-lang#94438, then removed in rust-lang#94596. Both of these PRs were beta-backported in rust-lang#94933, but I think there was a mistake in the order they were applied or this removal was overlooked. I think this fixes the remaining issues referenced in rust-lang#94511 (comment). Not sure this is the correct way to put something up for beta-backport, but the PR is at least open so it can be referenced and the commit can be cherry-picked. Feel free to close this PR. r? `@Mark-Simulacrum` cc: rust-lang#94511
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of including slightly more complicated logic in
check_argument_typesto fix the bug (#94516) I introduced in #94438, and inevitably have this bug appear once again when some other diagnostic is written that causescheck_exprto be called an expression during a (bad) code path, just delay the bug in adjustment logic.I am open to other implementations that don't delay the bug here.
Fixes #94516